I have a program running on a W7 PC that requires that several IP addresses be assigned to the PC in addition to a static address. The addresses are entered in the "Advanced TCP/IP Settings" under the "IP Settings" tab for the TCP/IPv4 properties of the Local Area Connection. The problem is that after I add the additional IP addresses and reboot the PC, it can no longer access, or be accessed, by the other PC\servers on the network by URL's (e.g. \\mediaserver) resulting in the error code "x80070035". IP addresses (e.g. 192.168.10.xxx) continue to work. Interestingly, the same problem arises when these changes are made to a Vista PC, but not to an XP one or a Mac running OSX. It should be noted that all the PC's and other devices network well together including some with static configurations until the multiple IP's are assigned to a W7/Vista PC. It would appear that the URL for the PC cannot be converted to a single IP address because the PC has being assigned multiple ones. Since there is a setting that allows for more than one IP for a device, there must me another one somewhere to assign only one of them to a URL. Any help would be appreciated.

Hi, If you set multiple IP address in TCP/IP settings, it will mess the router table. The error message "0x80070035 network path not found" indicates this PC cannot find the destination. If could be the incorrect router table or Metric. In addition, please understand TCP/IP protocol makes some improvements from Windows Vista. It is more security. Based on the current situation, I suggest enabling NetBIOS over TCP/IP for testing. 1) Go to "Control Panel -> Network and Internet ->Network Connections". 2) Right-Click on the connection and choose Properties. 3) Click "Internet Protocol (TCP/IP) Version 4" in the list. 4) Click Properties, and then click Advanced. 5) On the Advanced TCP/IP settings windows, go to "WINS" tab. 6) Under NetBIOS setting, click "Enable NetBIOS over TCP/IP", and then click OK. However, if the issue persists, it is not recommended to use that way in TCP/IP settings. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Thanks, Niki, for the reply. I have already tried enabling NetBIOS over TCP/IP with no success. You mentioned "Metric" which is currently set to automatic, the default value. Could you elaborate a bit on what this parameter is and what settings might be worth while trying?

Hi, I suggest you compare with the two routing table. When the computer can work properly, open an elevated command and type: route print -> c:\normal.txt and you will find normal.txt under C:\. When the computer occurs the issue, open an elevated command and type: route print -> c:\abnormal.txt. Also, I suggest comparing the TCP/IP configuration as well. Use the command ipconfig /all on the both situation and see the difference. You could upload the files to SkyDrive and I will help you look it. Best Regards, Niki Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I would appreciate it if you would have a look at the posted "normal" and "abnormal" files and see if anything pops out at you as being pertinent to my problem. Several things look odd to me, namely, the 3 IP address all shown as being "preferred" in the "abnormal" printout and the router address is included as a DNS in the "normal", but not the "abnormal" printout. It is the router that converts a URL to an IP address on the local network and it not being declared a DNS would certainly explain my problem, if I understand the DNS function correctly in this case. Skydrive links to requested`files: http://cid-824a7bf782221742.office.live.com/self.aspx/.Public/abnormal7.txt http://cid-824a7bf782221742.office.live.com/self.aspx/.Public/normal7.txt Note that I have included the "Route Print" and "IPconfig/all" results in the same file for each configuration (i.e. "Normal" and "Abnormal"), for easier reference and comparison. Thanks again for the help.

Technically it's not a URL but UNC... Anyway, your problem is with DNS. You're using your router for internal DNS resolution and a router isn't a true DNS device. Allow me to explain: The "DNS" that your router handles is basically a lookup in its DHCP table. In other words it intercepts the DNS request, looks for a corresponding entry in its DHCP table and returns that address. If it doesn't find an entry it forwards the request to the external DNS servers on the WAN side of the connection. What's happening in your case is that once you set a static address, that device no longer appears in the router's DHCP table and it's forwarding traffic meant for that device to the external WAN. And because the router isn't a true DNS server it can't accept dynamic updates from non-DHCP clients, nor can you manually add a Host (A) record. XP and some of the other systems will continue to work even with static addresses because they can fall back on NetBIOS for name resolution if a DNS query fails. Windows 7 (and Vista) rely almost exclusively on DNS and seem to only use NetBIOS when DNS isn't present at all, not just when it fails. You have two possible solutions to this issue: 1. Set up a true DNS server using either Windows Server (2003 or 2008 work well for this) or Linux or 2. Add the machines with static addresses to each device's HOSTS file. Queries to the HOSTS file happen before queries to the DNS servers. The Name Resolution lookup order is HOSTS->DNS(if present)->WINS(if present)->NetBIOS. Hope that helps some.

Thanks, Bob, for your very clear explanation of the cause of my problem which confirmed my suspicions about the router not properly performing the DNS function after changing the IPv4 settings. After some study, I went with the HOSTS file option and this seems to have solved the problem. Worth noting: simply assigning a static address to a device does not cause a UNC problem, leastwise not on the 3 PC's and 4 OS's that I have experimented with. The thing that causes the problem is assigning a static address AND multiple IP's to the same device. Anyway, you can't argue with success so I will mark the thread as answered.